Set-up Database view

Administration DBA Set-up Database Set-up Database view

The Set-up Database view enables you to load initial reference data, and to create and delete test data in the N4 database.

This option is not available if your N4 TOS is hosted by Kaleris.

You can use this view to setup initial data for a facility that is not yet live. You must use extreme caution when performing any task in this view. Navis recommends that you restrict access to the Set-up Database view to administrators only, by assigning the associated privilege (Database - Manage) only to users with administrative roles. For more information on privileges and roles, see Privileges view (on page 1) and Roles view (on page 1).

The Set-up Database view displays different set of options based on the scope at which you login to N4. For more information about logging in at a particular scope level, see Select a scope level (on page 1).

The Set-up Generic Carrier Data button adds the generic carriers GEN_VESSEL, GEN_TRAIN, and GEN_TRUCK at an operator scope level. To view the generic carriers GEN_VESSEL and GEN_TRAIN, you should have already created at least a single vessel visit and a train visit.

Global Scope Level

At the Global scope level, the Set-up Database view displays the following buttons:

• Generate ISO Codes: Adds the standard equipment types to the Equipment Types view at a global scope level. N4 also associates the equipment types with the appropriate icons that XPS uses to represent the equipment type.

• Import UNLOC Codes: Adds the UNLOC codes to the UN Locations view at a global scope level.

• Import Line Operators: Adds a default list of master organizations to the Master Organizations view (on page 1) at a global scope level.

Lower Scope Levels

At the lower scope levels, the Set-up Database view displays the following buttons:

• Delete Working Data!: Deletes all of the working data for your complex prior to a go-live, including:

• All of the equipment records

• Vessel visits

• Railcar visits

The Delete Working Data! does not delete the generic carriers (GEN_TRUCK, GEN_VESSEL, GEN_TRAIN, GEN_RAILCAR, and GEN_CARRIER) from N4.

• Bills of lading

• Equipment orders

• Gate transactions

• Road inspections

• TBD units

• EDI interchanges and batches

• Document Message

• Appointments

• Truck Visit Appointments

• Integration Errors

• Web Service Logs

• Carrier Visit Service Type

• Service Order

• Service Order Item

• Cargo Service Order

• Cargo Service Order Item

• Line Loadlist

• Line Dischargelist

• Chargeable Appointment Event

• Import Delivery Order

• Carrier Visit Service Order

• Move Record

• Vessel Visit Statistics

• Carrier Statistics

• Crane Activity

Use extreme caution, the Delete Working Data! option deletes all of the working data for your complex irrespective of the scope at which you are logged in. For example, if you are logged in at Facility1 when you click Delete Working Data!, N4 deletes all operational data for the complex, the facility you are logged in at and any other facilities within the complex.

This option does not delete report designs, report definitions, configurations, settings, and reference data, such as line operators and equipment types.

N4 deletes the reference data from the Point of Work entity and disconnects any dependencies between the following combination of entities:

• EqBaseOrder and Hazards

• ItemServiceTypeUnits and Events

The ARGODELETE_WORKING_DATA001 (DELETE_WORKING_DATA_SKIP_EQUIPMENT_STATE) (on page 1) setting determines if the Equipment State table is deleted when using the Delete Working Data! action.

Navis recommends that you do not depend only on this feature for the go-live day. Follow the steps below to completely remove working data.

Use the Delete Working Data! action only after you have defined all the reference data in N4.

To remove working data before go-live:

1.  Halt all background jobs (Administration > System > Background Jobs > Action > Halt Job).

2.  Run the Delete Working Data! action (Administration > DBA > Set-up Database > Delete Working Data!).

3.  Since new events will be created while deleting some entities, repeat the Delete Working Data! action.

4.  Delete work assignments by using the Launch Database Purge/Archive action (Administration > System > Background Jobs > Actions> Launch Database Purge/Archive). The work assignments are deleted based on the PURGE_WORK_ASSIGNMENTS setting. (The default is 2 days.)

5.  Manually clean up any pending entities from the database.

6.  Take a database dump from the test environment.

7.  Restore the database dump as the production database on the go-live day.

• Create/Update Default Gates: Adds the following standard gate configurations to N4 at an operator scope level:

• Main gate with a one-stage ingate and outgate, for non-XPS operations only.

• Main gate with a multistage ingate (callup, kiosk, and office stages) and an automated outgate (yard stage), for XPS operations.

• Empty gate with a two-stage ingate (kiosk and office stages) and an automated outgate (yard stage), for XPS operations.

• Set-up Basic Reports: Adds a list of standard report designs to the Report Designs view (on page 1) at an operator scope level. Use this option to set-up basic reports, which you can modify for your operations. This option is available only with Monitor and Analytics license.

Use this option only once, this option will overwrite any modifications to the standard report designs.

• Set-up Basic Event Data: Adds a list of standard event types to the Event types view at a global scope level.

• Set-up Generic Carrier Data: Adds the generic carriers, GEN_VESSEL, GEN_TRAIN, and GEN_TRUCK to N4.

You need to use this option only if you want to see the default carriers, GEN_VESSEL, GEN_TRAIN, and GEN_TRUCK, in the Carrier O/B Intended and Carrier O/B Declared LOVs in the Routing form without creating at least one vessel visit or train visit.

• Set-up EDI Message Types and Maps: Adds the supported EDI message types and respective Navis standard EDI message maps at an operator scope level. The standard EDI message map contains the standard mapping file and data dictionary file.

Use this option to initially setup EDI, to add new supported EDI messages, or to update the EDI message maps for the supported EDI messages. For more information on EDI message types and a list of the supported EDI message types, see EDI Message Type form.

• Update All Billable Events as Extracted: Marks all billable service events that were recorded on or before a specific date as already invoiced. This ensures that N4 does not include these events when the user starts the billable event extract.

When you click the button, N4 prompts you for confirmation. If you click Yes, N4 displays the Update All Billable Events as Extracted form (on page 1) to enable you to enter a date. All events that were recorded on or before this date are marked as extracted.

Before they start using the N4 Billing for the first time, existing N4 users can use this option to delete historic events that they may have already billed using an external billing system.

• Create missing storage/reefer event extract records: Creates the Reefer and Storage events in the Chargeable Unit Events view for all the Active units in the yard. You can use these events to invoice storage charges for all containers and power charges for reefer containers.

For the Storage event, N4 uses the Time Facility-In as the Start Time for the event. For the Reefer event, N4 uses the time when the first UNIT_POWER_CONNECT event is recorded as the Start Time for the event.